E-mail route trace functionality

ABSTRACT

An example of a solution provided here comprises: in response to a request from an original sender, transmitting tracing notifications to the original sender, and providing limits for the tracing notifications. The tracing notifications operate when an e-mail message is forwarded to at least one non-original recipient.

CROSS-REFERENCES TO RELATED APPLICATIONS, AND COPYRIGHT NOTICE

The present application is related to a co-pending patent applicationentitled Method and System for Multiple-Party, Electronic Mail Receipts,filed on even date herewith. This co-pending patent application isassigned to the assignee of the present application, and hereinincorporated by reference. A portion of the disclosure of this patentdocument contains material which is subject to copyright protection. Thecopyright owner has no objection to the facsimile reproduction by anyoneof the patent document or the patent disclosure, as it appears in thePatent and Trademark Office patent file or records, but otherwisereserves all copyright rights whatsoever.

FIELD OF THE INVENTION

The present invention relates generally to electronic mail (e-mail), andmore particularly to methods and systems for notifying users of thedisposition of messages.

BACKGROUND OF THE INVENTION

In many situations, the original sender of an e-mail message would liketo know who, besides the original recipient, has read the message. Thisis true of a person who, in a corporate environment, sends a messagethat is politically charged, or a business person who sends an e-mailnewsletter to customers, to give just two examples. However,conventional e-mail implementations allow an original recipient of amessage to forward the message to any number of people, without theknowledge of the original sender of the message. Conventional receiptnotifications merely inform the original sender that the originalrecipient has read the message. Thus there is a need for systems andmethods that address this gap in conventional approaches to e-mail.

SUMMARY OF THE INVENTION

An example of a solution to problems mentioned above comprises: inresponse to a request from an original sender, transmitting tracingnotifications to the original sender, and providing limits for thetracing notifications. The tracing notifications operate when an e-mailmessage is forwarded to at least one non-original recipient.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained when thefollowing detailed description is considered in conjunction with thefollowing drawings. The use of the same reference symbols in differentdrawings indicates similar or identical items.

FIG. 1 illustrates a simplified example of a computer system capable ofperforming the present invention.

FIG. 2 is a high-level block diagram illustrating an example of a methodand system for providing e-mail services according to the teachings ofthe present invention.

FIG. 3 is a flow chart illustrating an example of a method for sendingelectronic mail, according to the teachings of the present invention.

FIG. 4 is a diagram illustrating an example of output for a user,according to the teachings of the present invention.

DETAILED DESCRIPTION

The examples that follow involve the use of one or more computers, andmay involve the use of one or more communications networks, or the useof various devices capable of handling e-mail, such cell phones ortwo-way pagers. The present invention is not limited as to the type ofcomputer or other device on which it runs, and not limited as to thetype of network used.

The following are definitions of terms used in the description of thepresent invention and in the claims:

“Application” means any specific use for computer technology, or anysoftware that allows a specific use for computer technology.

“Comparing” means bringing together for the purpose of finding anylikeness or difference, including a qualitative or quantitative likenessor difference.

“Component” means any element or part, and may include elementsconsisting of hardware or software or both.

“Computer-usable medium” means any carrier wave, signal or transmissionfacility for communication with computers, and any kind of computermemory, such as floppy disks, hard disks, Random Access Memory (RAM),Read Only Memory (ROM), CD-ROM, flash ROM, non-volatile ROM, andnon-volatile memory.

“Notification” means any notification message that reports thedisposition of another message.

This is traditionally called a “Message Disposition Notification” (MDN),“read receipt,” “acknowledgment,” or “receipt notification.” Thesetraditional terms may be used here, even though the details of MDN'sdescribed here differ from traditional MDN's.

“Output” or “Outputting” means producing, transmitting, or turning outin some manner, including but not limited to printing on paper, ordisplaying on a screen, writing to a disk, or using an audio device.

“Selection signal” means any signal from a user who is making aselection, utilizing any input device, including a keyboard,speech—recognition interface, or pointing device such as a track ball, ajoy stick, a touch—sensitive tablet or screen, or a mouse.

“Storing” data or information, using a computer, means placing the dataor information, for any length of time, in any kind of computer memory,such as floppy disks, hard disks, Random Access Memory (RAM), Read OnlyMemory (ROM), CD-ROM, flash ROM, non-volatile ROM, and non-volatilememory.

“Tag” means any element, label, field, or value that conveys informationabout a message, or about how to handle a message.

“Tracing notification” means any notification message that reports thedisposition of another message after it has been successfully forwardedto a non-original recipient.

FIG. 1 illustrates a simplified example of an information handlingsystem that may be used to practice the present invention. The inventionmay be implemented on a variety of hardware platforms, includingembedded systems, cell phones, two-way pagers, hand-held computers,personal computers, workstations, servers, and mainframes. The computersystem of FIG. 1 has at least one processor 110. Processor 110 isinterconnected via system bus 112 to random access memory (RAM) 116,read only memory (ROM) 114, and input/output (I/O) adapter 118 forconnecting peripheral devices such as disk unit 120 and tape drive 140to bus 112. The system has user interface adapter 122 for connectingkeyboard 124, mouse 126, or other user interface devices such as audiooutput device 166 and audio input device 168 to bus 112. The system hascommunication adapter 134 for connecting the information handling systemto a communications network 150, and display adapter 136 for connectingbus 112 to display device 138. Communication adapter 134 may link thesystem depicted in FIG. 1 with hundreds or even thousands of similarsystems, or other devices, such as remote printers, remote servers, orremote storage units. The system depicted in FIG. 1 may be linked toboth local area networks (sometimes referred to as intranets) and widearea networks, such as the Internet.

While the computer system described in FIG. 1 is capable of executingthe processes described herein, this computer system is simply oneexample of a computer system. Those skilled in the art will appreciatethat many other computer system designs are capable of performing theprocesses described herein.

FIG. 2 is a high-level block diagram illustrating an example of a methodand system for providing e-mail services according to the teachings ofthe present invention. A system like this could operate via an intranet,or the Internet, for example, or via some other network (shown at 220).At the upper left, a user named John (not shown) is the original senderof an e-mail message 201. The system allows e-mail communication from asender, using sender's e-mail client 230, to recipient's e-mail client240. The sender's e-mail client 230 receives input from the sender,specifying a recipient named Sue at recipient's e-mail client 240, andrequesting tracing notifications, for an e-mail message 201. The e-mailmessage 201 is transmitted to the recipient's e-mail client 240, throughnetwork 220. At 202, the e-mail message is forwarded or re-transmittedfrom Sue's e-mail client 240 to non-original recipients named Mary andBill, who utilize e-mail clients at 250. In this example, Sue is theoriginal recipient. Later recipients to whom the e-mail message isforwarded are referred to as non-original recipients.

An e-mail notification message that reports the disposition of anothermessage, after it has been successfully delivered to a recipient, istraditionally called a “Message Disposition Notification” (MDN), “readreceipt,” “acknowledgment,” or “receipt notification.” These terms areused here, even though the details of MDN's described here differ fromtraditional MDN's. Receipt notifications or MDN's are transmitted (at204) from each non-original recipient's e-mail client at 250 to sender'se-mail client 230, through network 220.

To summarize the example so far, FIG. 2 involves the following: inresponse to a request from an original sender (at 230), transmittingtracing notifications (204) to the original sender; and providing limits(270) for the tracing notifications. The tracing notifications (204)operate when an e-mail message is forwarded (202) to at least onenon-original recipient (at 250). Providing limits (270) may involve oneor more limiting actions such as: limiting the time during which thetracing notifications operate, limiting the number of retransmissionsfor which the tracing notifications operate, limiting the tracingnotifications' operation, based on a domain policy, limiting the contentof the tracing notifications, and discontinuing the tracingnotifications, in response to a signal from the original sender.

Continuing with details of the example in FIG. 2, the e-mail message isagain forwarded at 203, from e-mail clients at 250 to non-originalrecipients Jose and any number of others (symbolized by “N,” because theothers could be numbered from 1 to N), who utilize e-mail clients at260. MDN's are transmitted (at 205) from each non-original recipient'se-mail client at 260 to sender's e-mail client 230, through network 220.E-mail clients at 230, 240, 250 and 260 may comprise any software andhardware capable of handling e-mail.

Transmitting tracing notifications (204 or 205) may involve signalingthat the content of the e-mail message has been provided to at least onenon-original recipient (at 250 or 260), or signaling that the e-mailmessage has been forwarded to (not necessarily opened by) at least onenon-original recipient (at 250 or 260).

The example in FIG. 2 involves receiving tracing notifications. Arrows204 and 205, with heads pointing to original sender's e-mail client 230,symbolize tracing notifications being received by original sender'se-mail client 230. The example involves providing to a user (John, theoriginal sender, at 230) information (based on MDN's 204 and 205) as towho has been provided with the content of the e-mail message 201. Thisinformation would identify Mary and Bill, who were provided with themessage content via the forwarding at 202. This information also wouldidentify Jose and N, who were provided with the message content via theforwarding at 203. Storing and updating the information may also beinvolved. This may be accomplished by the original sender saving theMDN's 204 and 205 as they arrive. Storing and updating the informationmay also be organized and automated to some degree (using notificationdatabase 210 for example). Notification database 210 may be a componentof sender's e-mail client 230, or notification database 210 may beseparate from, but accessible to, sender's e-mail client 230.

Continuing with details of the example in FIG. 2, original sender'se-mail client 230 may serve as means for receiving from the originalsender a request for tracing notifications, for e-mail message 201.Original sender's e-mail client 230 may serve as means responsive to therequest, for creating at least one tag for e-mail message 201,indicating that the original sender is to receive tracing notifications.The message is tagged and sent at 201. The message is forwarded (at 202or 203) to a non-original recipient's e-mail client (at 250 or 260),which may serve as means responsive to the tag, for transmitting thetracing notifications (MDN's 204 and 205) to the original sender. Jose'se-mail client (at 260) may serve as means for signaling (at 205) thatthe content of the e-mail message has been provided to non-originalrecipient Jose. Mary's e-mail client (at 250) may serve as means forsignaling (at 204) that the e-mail message has been forwarded (at 203)to non-original recipient Jose (at 260).

The example in FIG. 2 involves means for providing limits for tracingnotifications. An original sender's e-mail client 230 and a non-originalrecipient's e-mail client (at 250 or 260) may serve as means forproviding limits. For example, consider means for limiting the timeduring which tracing notifications (MDN's) operate. An original sender'se-mail client 230 sets an expiration date. Then a non-originalrecipient's e-mail client (at 250 or 260) enforces the expiration date,by following a rule such as “do not send the MDN if the expiration datehas passed.”

As another example, consider means for limiting the number ofretransmissions for which tracing notifications operate (i.e. a hoplimit). An original sender's e-mail client 230 sets a maximum number ofretransmissions. The actual number of retransmissions is stored, andincremented each time the message is forwarded (at 202 or 203). Then anon-original recipient's e-mail client (at 250 or 260) enforces thelimit, by following a rule such as “do not send the MDN unless theactual number of retransmissions is less than or equal to maximum numberof retransmissions.”

As another example, consider means for limiting the content of thetracing notifications. A non-original recipient's e-mail client (at 250or 260) may provide some privacy protection for a non-original recipientby including in a tracing notification only the person's name, and notthe e-mail address of non-original recipient's e-mail client (at 250 or260).

In FIG. 2, limiter 270 symbolizes a centralized way to implement limits.Arrows passing through network 220 symbolize messages passing throughvarious network components. MDN's 204 and 205, passing near limiter 270,symbolize that one or more components such as an e-mail routing systemor a mail server follow rules to impose limits. For example, considermeans for limiting the time during which tracing notifications (MDN's)operate. A mail server enforces a policy of not tracing old messages, byfollowing a rule such as “do not send the MDN if the original message isdated over one year before today's date.”

As another example, consider means responsive to a signal from theoriginal sender, for discontinuing tracing notifications (i.e. turningoff tracing). A mail server stops tracing, by following a rule such as“do not send the MDN if a ‘discontinue tracing’ signal has been receivedfor this message.” As another example, consider limiting thetransmitting of tracing notifications, based on a domain policy. Ane-mail routing system refuses to send MDN's in some cases, based on thedomain of original sender's e-mail client 230, by following a rule suchas “do not send the MDN if the message originates in domain X,” or “donot send the MDN if the message originates outside of this corporateintranet.”

FIG. 3 is a flow chart illustrating an example of a method for sendingelectronic mail, according to the teachings of the present invention.The process starts at 310, which may represent a user (sender) launchingan e-mail application in preparation for sending electronic mail to oneor more recipients. At decision 320, the “No” branch may be taken, forexample if the sender decides to send the message without requesting anytracing notifications. In that case, the sender would proceed directlyto writing and editing the message (350) and sending the message withconventional tags (360).

On the other hand, if any tracing notifications are desired, the “Yes”branch may be taken at decision 320, symbolizing receiving from anoriginal sender a request for tracing notifications, for an e-mailmessage. Then the next step in this example is providing a menu, 330.This is a way of receiving input from the sender, specifying limits fortracing notifications, and other options for the e-mail message. Anumber of features may be present here. One possibility is providingpredefined limits. Another possibility is automatically providingdefault behavior, in the absence of contrary input from the sender.

The input is received from the sender at 340, to set limits. Forexample, the sender may, via a selection signal, specify one or morelimiting actions such as:

-   (1) limiting the time during which the tracing notifications    operate,-   (2) limiting the number of retransmissions for which the tracing    notifications operate,-   (3) discontinuing the tracing notifications, in response to a signal    from the original sender.

Next, writing and editing the message is allowed, 350. Then the messageis tagged and sent at 360. This involves creating at least one tag forthe e-mail message, indicating that the original sender is to receivethe tracing notifications. Creating a tag is in response to the originalsender's request at 320 for tracing notifications. For example, ane-mail application may use Transmission Control Protocol (TCP) anddeliver a separate copy of the message to each recipient's mailbox. Theproper tag is applied to each copy. With the sending accomplished, theprocess ends at 370 in this example. See also FIG. 2 concerning thereceiving of tracing notifications, and FIG. 4 concerning output basedon receiving tracing notifications.

Regarding FIG. 3, the order of the operations in the processes describedabove may be varied. For example, it is within the practice of theinvention for a user to follow the path from block 310 to block 340, andchoose an option to turn off tracing for a message sent earlier. Then,proceeding directly to block 360, a “discontinue tracing” message may besent to a mail server. Those skilled in the art will recognize thatblocks in FIG. 3 could be arranged in a somewhat different order, butstill describe the invention. Blocks could be added to theabove-mentioned diagram to describe details, or optional features; someblocks could be subtracted to show a simplified example.

Turning now to details that may be involved in FIG. 3, consider theoperation where the message is tagged and sent at block 360. Animplementation of tracing notifications may use tags to conveyinformation about how to handle a message. Some predefined,general-purpose tags for e-mail messages are well-known, but the tagsdescribed here are new, and they convey information about new kinds ofmessage handling. Various implementation methods may be used for thepresent invention. Two implementation factors may be considered. Onefactor is incorporation of metadata into the message, including thee-mail address of the original sender. For example, consider ahypothetical field named “MailOriginator,” upon which special actionsmay be taken. This might be added to a message, and would identify theoriginal sender of a message. A second factor is the reading of suchmetadata by an e-mail application.

The present invention may use any tags that are understood by both thesender's software and the recipient's software. A unique implementationscheme could be used for an organization's internal e-mail system, forexample. On the other hand, the present invention may be implemented bybuilding upon well-known standards for e-mail.

Some examples of standards are: Simple Mail Transfer Protocol (SMTP),Multipurpose Internet Mail Extensions (MIME), and Secure MultipurposeInternet Mail Extensions (S/MIME). Regarding such standards, referenceis made to the following documents: Jonathan B. Postel, Request forComments (RFC) # 821, Simple Mail Transfer Protocol, 1982; David H.Crocker, RFC # 822, Standard for the Format of ARPA Internet TextMessages, 1982; J. Palme, RFC # 2076, Common Internet Message Headers,1997; and R. Fajman, RFC # 2298, An Extensible Message Format forMessage Disposition Notifications, 1998. An Internet e-mail messageconsists of two parts: a header and a body. A header may be used toimplement the present invention. A header has a collection offield—value pairs that convey information about the message. Forexample, a hypothetical field named “MailOriginator” might have a valueof “john@acmecorp.com” to identify the original sender of a message.

One example given in RFC # 2298 is the field“Disposition-Notification-To,” with a value of at least one mailbox.However, “confirmation from the user SHOULD be obtained (or no MDN sent). . . if there is more than one distinct address in theDisposition-Notification-To header,” according to RFC # 2298. ADisposition-Notification-To header in a message is merely a request fora Message Disposition Notification (MDN).

Extension fields provide a way to implement tracing notifications bybuilding upon the standard described in RFC # 2298. Extension-fieldnames beginning with “X-” are not defined as standard fields; such namesare reserved for experimental use, according to RFC # 2298. The name ofthe application should follow the “X-.”

For example, consider an extension field named“X-Tracemail-Tracing-Notification-To,” with a value of at least onemailbox (the original sender's e-mail address). This example is for ane-mail application named “Tracemail” that would implement tracingnotifications. This extension field would have a persistent quality,serving as a continuous request for MDN's, any time the message isforwarded. This example assumes that this tag is applied to a message bythe original sender's software (at block 360 of FIG. 3), and understoodby the non-original recipient's software. Then the non-originalrecipient's software sends an MDN to the original sender's e-mailaddress, and leaves this extension field intact for later use, when themessage is forwarded again.

Continuing with details that may be involved in FIG. 3, extensiblemarkup language (XML), provides a way of containing and managinginformation that is designed to handle data exchange among various datasystems. Thus it is well-suited to implementation of the presentinvention. Reference is made to the book by Elliotte Rusty Harold and W.Scott Means, XML in a Nutshell (O'Reilly & Associates, 2001). As ageneral rule, XML messages use “attributes” to contain information aboutdata, and “elements” to contain the actual data.

Tracing notifications may be implemented by building upon an XML-basedstandard such as e-business XML (ebXML), and in particular the ebXMLMessaging Service. Reference is made to an article by Pim van der Eijk,The ebXML Messaging Service, (O'Reilly & Associates, 2003), available atO'Reilly's XML.com web site. The ebXML Messaging Service specificationextends the Simple Object Access Protocol (SOAP) specification toprovide security and reliability features. The ebXML Messaging Servicespecification may be used to transfer messages over SMTP, HypertextTransfer Protocol (HTTP), or some other communications protocol. Thereare no restrictions on the message content. Users have a choice of ebXMLMessaging Service implementations, provided by different vendors,including open source implementations.

Regarding receipt notifications, ebXML Messaging Service defines anoptional <eb:AckRequested> extension element for the <SOAP:Header>. Theresponding message handler can send a message containing an<eb:Acknowledgment> extension element, with an <eb:RefToMessageld>element to specify which message is being acknowledged.

Reference is made to the specification by the Organization for theAdvancement of Structured Information Standards (OASIS) TechnicalCommittee, ebXML Messaging Services Specification 2.0 (OASIS 2002).Multi-hop reliable messaging is accomplished using the AckRequestedelement, and an Acknowledgment Message containing an Acknowledgmentelement, each with a SOAP actor of Next MSH.

The ebXML Messaging Service specification gives the following example ofthe AckRequested element targeted at the next message handler (NextMSH).In the following example, an Acknowledgment Message is requested of thenext message handler:

-   <eb:AckRequested SOAP:mustUnderstand=“1” eb:version=“2.0”    eb:signed=“false”    SOAP:actor=“urn:oasis:names:tc:ebxml-msg:actor:nextMSH”/>

The ebXML Messaging Service specification gives the following rule: “Ifan AckRequested element is present, then generate an AcknowledgmentMessage in response (this may be as part of another message).”

The ebXML Messaging Service specification gives the following example ofan Acknowledgment Message with the Acknowledgment element targeted atthe next message handler node along the reverse message path (theSending MSH):

-   <eb:Acknowledgment SOAP:mustUnderstand=“1”    eb:version=“2.0”SOAP:actor=“urn:oasis:names:tc:ebxml-msg:actor:nextMSH”>-   <eb:Timestamp>2001-03-09T12:22:30</eb:Timestamp>-   <eb:RefToMessageId>323210:e52151ec74:-7ffc@xtacy</eb:RefToMessageId>-   <eb:From><eb:PartyId>uri:www.example.com</eb:PartyId></eb:From>-   </eb:Acknowledgment>

Tracing notifications may be implemented by building upon the ebXMLMessaging Service as follows. For example, consider a new extensionelement named “TracingAckRequested.” This example assumes that this tagis applied to a message by the original sender's software (at block 360of FIG. 3), and understood by the non-original recipient's software. Newbehavior for tracing notifications could be specified, so that an e-mailapplication follows a rule such as: “If a TracingAckRequested element ispresent, then generate an Acknowledgment Message in response, and sendit directly (not along the reverse message path) to the original senderidentified in the From element.” The TracingAckRequested element istargeted at any non-original recipient (analogous to the NextMSH). TheTracingAckRequested element needs to continue to appear on the SOAPmessage destined to the next message handler, so the TracingAckRequestedelement needs to be reapplied by each message handler.

FIG. 4 is a diagram illustrating an example of output for a user,according to the teachings of the present invention. To begin with anoverview, FIG. 4 shows a user interface 401 for an original sender. Theexample in FIG. 4 involves output, based on receiving tracingnotifications that operate when the e-mail message is forwarded to atleast one non-original recipient. FIG. 4 shows an example of providingto a user a representation (at 410 or 405 or both) of the e-mailmessage, together with information (at 420) as to who has perceived thecontent of the e-mail message, or who has been provided with the contentof an e-mail message. A user interface like this could be used with amethod and system like the one shown in FIGS. 2-3. A user interface likethis could be displayed with text and graphics, as shown at 401. Anaudible interface also could be provided to the sender via audio output.

Turning to details of FIG. 4, interface 401 provides output, based onreceiving tracing notifications that operate when the e-mail message isforwarded to at least one non-original recipient. At the top ofinterface 401 is a representation of a message, at 410, including amessage identifier such as a “subject” description, or an identificationnumber. Also included in the representation of the message at 410 arethe date of the message and the names of sender and recipient. Inanother format, an interface like 401 may provide representations of anumber of messages. A user may pick a message of interest from a list,for example.

In interface 401 there is a section 420 showing who has opened thismessage. In this example, three recipients listed at 411, 412, and 413have opened this message. An optional feature is providing or displayingat least some of the content of a message at 405, as a representation ofa message. The content, visible or accessible at 405, may include text,graphics, audio content or video content. In other words, FIG. 4 showsan example of means for providing to a user a representation (at 410 or405 or both) of the e-mail message, together with information (at 420)as to who has been provided with the content of the e-mail message.

Information provided in section 420, showing who has opened thismessage, may change from time to time. This would involve storing andupdating the information, as discussed above in connection withnotification database 210 in FIG. 2. Section 420 may serve as means forsignaling that the content of the e-mail message has been provided to atleast one non-original recipient. Section 420 may serve as means forsignaling that the e-mail message has been forwarded to (not necessarilyopened by) at least one non-original recipient. Section 420 may provideoutput based on one or more kinds of tracing notifications such as:

-   (1) notifications reporting that the message has been sent somewhere    in some manner (e.g. forwarded or faxed),-   (2) notifications reporting that the message contents were provided    to someone reading a non-original recipient's mailbox,-   (3) notifications reporting deletion (perhaps without display) of    the message.

With an interface like 401, spoken input could be received from thesender via a speech recognition interface, or the sender might mark aword displayed on a screen. A user's input might specify a particularmessage that the user is interested in, or specify a particular behaviorfor the interface 401, for example.

In conclusion, we have shown examples of solutions that deliverinformation as to who has been provided with the content of an e-mailmessage.

One of the possible implementations of the invention is an application,namely a set of instructions (program code) executed by a processor of acomputer from a computer-usable medium such as a memory of a computer.Until required by the computer, the set of instructions may be stored inanother computer memory, for example, in a hard disk drive, or in aremovable memory such as an optical disk (for eventual use in a CD ROM)or floppy disk (for eventual use in a floppy disk drive), or downloadedvia the Internet or other computer network. Thus, the present inventionmay be implemented as a computer-usable medium havingcomputer-executable instructions for use in a computer. In addition,although the various methods described are conveniently implemented in ageneral-purpose computer selectively activated or reconfigured bysoftware, one of ordinary skill in the art would also recognize thatsuch methods may be carried out in hardware, in firmware, or in morespecialized apparatus constructed to perform the method.

While the invention has been shown and described with reference toparticular embodiments thereof, it will be understood by those skilledin the art that the foregoing and other changes in form and detail maybe made therein without departing from the spirit and scope of theinvention. The appended claims are to encompass within their scope allsuch changes and modifications as are within the true spirit and scopeof this invention. Furthermore, it is to be understood that theinvention is solely defined by the appended claims. It will beunderstood by those with skill in the art that if a specific number ofan introduced claim element is intended, such intent will be explicitlyrecited in the claim, and in the absence of such recitation no suchlimitation is present. For non-limiting example, as an aid tounderstanding, the appended claims may contain the introductory phrases“at least one” or “one or more” to introduce claim elements. However,the use of such phrases should not be construed to imply that theintroduction of a claim element by indefinite articles such as “a” or“an” limits any particular claim containing such introduced claimelement to inventions containing only one such element, even when thesame claim includes the introductory phrases “at least one” or “one ormore” and indefinite articles such as “a” or “an;” the same holds truefor the use in the claims of definite articles.

1. A method for providing electronic mail (e-mail) services, said methodcomprising: receiving from an original sender a request for tracingnotifications, for an e-mail message; in response to said request,creating at least one tag for said e-mail message, indicating that saidoriginal sender is to receive said tracing notifications; receiving at acomputing device of the original sender said tracing notifications fromone or more non-original recipients in response to said e-mail messagebeing forwarded by an original recipient to at least one non-originalrecipient; and providing limits for said tracing notifications, whereinsaid providing limits further comprises: limiting a number ofretransmissions for which said tracing notifications operate, whereinlimiting the number of retransmissions for which tracing notificationsoperate further comprises: setting a maximum number of retransmissionsfor the email message, incrementing an actual number of retransmissionsof the email message each time the email message is forwarded from theoriginal recipient to the one or more non-original recipients,responsive to the actual number of retransmissions being less than orequal to the maximum number of retransmissions, transmitting the emailmessage from the original recipient to the one or more non-originalrecipients, and responsive to the actual number of retransmissions beingmore than the maximum number of retransmissions, refusing to transmitthe email message from the original recipient to the one or morenon-original recipients, and limiting the content of said tracingnotifications, wherein limiting the content of the tracing notificationstransmitted to the original sender limits the content of the tracingnotifications to only a name of the non-original recipient whileexcluding an e-mail address of the non-original recipient.
 2. The methodof claim 1, further comprising: providing to a user a representation ofsaid e-mail message, together with information as to who has beenprovided with the content of said e-mail message.
 3. The method of claim2, further comprising: storing and updating said information.
 4. Themethod of claim 1, further comprising: transmitting said tracingnotifications to said original sender, from said at least onenon-original recipient.
 5. The method of claim 4, wherein saidtransmitting tracing notifications further comprises transmitting one ormore tracing notifications selected from a group consisting of:notifications reporting that said message has been sent somewhere insome manner, notifications reporting that the content of said messagewas provided to said at least one non-original recipient, andnotifications reporting deletion of said message.
 6. A method forproviding e-mail services, said method comprising: in response to arequest from an original sender, transmitting tracing notifications to acomputing device of said original sender from one or more non-originalrecipients in response to an e-mail message being forwarded by anoriginal recipient to at least one non-original recipient; and providinglimits for said tracing notifications, wherein said providing limitsfurther comprises: limiting a number of retransmissions for which saidtracing notifications operate, wherein limiting the number ofretransmissions for which tracing notifications operate furthercomprises: setting a maximum number of retransmissions for the emailmessage, incrementing an actual number of retransmissions of the emailmessage each time the email message is forwarded from the originalrecipient to the one or more non-original recipients, responsive to theactual number of retransmissions being less than or equal to the maximumnumber of retransmissions, transmitting the email message from theoriginal recipient to the one or more non-original recipients, andresponsive to the actual number of retransmissions being more than themaximum number of retransmissions, refusing to transmit the emailmessage from the original recipient to the one or more non-originalrecipients, and limiting the content of said tracing notifications,wherein limiting the content of the tracing notifications transmitted tothe original sender limits the content of the tracing notifications toonly a name of the non-original recipient while excluding an e-mailaddress of the non-original recipient.
 7. The method of claim 6, whereinsaid transmitting tracing notifications further comprises: signalingthat the content of said e-mail message has been provided to said atleast one non-original recipient.
 8. The method of claim 6, wherein saidtransmitting tracing notifications further comprises: signaling thatsaid e-mail message has been forwarded to said at least one non-originalrecipient.
 9. The method of claim 6, further comprising: providing to auser a representation of said e-mail message, together with informationas to who has been provided with the content of said e-mail message. 10.The method of claim 9, further comprising: storing and updating saidinformation.